Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Just a test #32456

Closed
tim-one opened this issue Jun 25, 2000 · 10 comments
Closed

Just a test #32456

tim-one opened this issue Jun 25, 2000 · 10 comments
Assignees

Comments

@tim-one
Copy link
Member

tim-one commented Jun 25, 2000

BPO 400622
Nosy @tim-one, @loewis
Files
  • None: None
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/tim-one'
    closed_at = <Date 2008-01-29.22:03:38.506>
    created_at = <Date 2000-06-25.03:20:31.000>
    labels = []
    title = 'Just a test'
    updated_at = <Date 2008-01-29.22:03:38.506>
    user = 'https://github.com/tim-one'

    bugs.python.org fields:

    activity = <Date 2008-01-29.22:03:38.506>
    actor = 'loewis'
    assignee = 'tim.peters'
    closed = True
    closed_date = None
    closer = None
    components = ['None']
    creation = <Date 2000-06-25.03:20:31.000>
    creator = 'tim.peters'
    dependencies = []
    files = ['2463']
    hgrepos = []
    issue_num = 400622
    keywords = ['patch']
    message_count = 10.0
    messages = ['32822', '32823', '32824', '32825', '32826', '32827', '32828', '32829', '32830', '61833']
    nosy_count = 2.0
    nosy_names = ['tim.peters', 'loewis']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'closed'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue400622'
    versions = []

    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    No description provided.

    @tim-one tim-one closed this as completed Jun 25, 2000
    @tim-one tim-one self-assigned this Jun 25, 2000
    @tim-one tim-one closed this as completed Jun 25, 2000
    @tim-one tim-one self-assigned this Jun 25, 2000
    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    Huh. Lotsa clicking needed to submit a patch via the web interface.

    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    So what does a second comment look like? First one took several minutes to complete after hitting "Submit Changes". Also, let's see whether structure is preserved in comments:
    if this is indented:
    hope this is indented more

    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    Bummer -- indentation is lost. Let's stick a blank line next:

    Actually stuck two there.

    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    So <bold>blank lines</bold> do show up. Response time varies from seconds to minutes, & unrelated to the amount of text typed into the "add a comment" box. Changing status to "Postponed" for the heck of it.

    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    At least under IE5, right-clicking on "View Raw Patch" and selecting "Save Target As ..." manages to download the patch directly to a file, although it suggests the less than useful filename "download.php" by default.

    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    Man, that last one took so long I stopped the browser and hit "Submit Changes" again. Only one copy of the comment showed up, which is good.

    Nice: SF is generated email to me each time the patch is updated. Unfortunately, I *suspect* this email goes only to the submittor, not also to the "assigned to" person. Check that later.

    What else ... mysterious "close_date" records showing up in the Patch Change History.

    1 similar comment
    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    Man, that last one took so long I stopped the browser and hit "Submit Changes" again. Only one copy of the comment showed up, which is good.

    Nice: SF is generated email to me each time the patch is updated. Unfortunately, I *suspect* this email goes only to the submittor, not also to the "assigned to" person. Check that later.

    What else ... mysterious "close_date" records showing up in the Patch Change History.

    @tim-one
    Copy link
    Member Author

    tim-one commented Jun 25, 2000

    OK, not so good: the last comment did show up twice. Marking deleted.

    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Jan 29, 2008

    This message links to msg32826

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 9, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    None yet
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant