Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org, Esben Skovenborg <esskov@oncable.dk>
Subject: Re: [PATCH] git svn: allow uppercase UUIDs from SVN
Date: Sun, 12 Jul 2009 14:53:06 -0700	[thread overview]
Message-ID: <7v7hydlgal.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vtz1hli15.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sun\, 12 Jul 2009 14\:15\:34 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Eric Wong <normalperson@yhbt.net> writes:
>
>>   Junio: pushed out to git://git.bogomips.org/git-svn along with
>>          some patches I think I forgot to tell you about:
>
> Thanks, will pull.

Actually I think I got something different from what I thought I was
expecting.  Your message said:

    Eric Wong (1):
          git svn: allow uppercase UUIDs from SVN

    Mattias Nissler (2):
          git-svn: Always duplicate paths returned from get_log
          git-svn: Fix branch detection when repository root is inaccessible

but after merge:

    Junio C Hamano (1):
          Merge git://git.bogomips.org/git-svn

    Mattias Nissler (2):
          git-svn: Always duplicate paths returned from get_log
          git-svn: Fix branch detection when repository root is inaccessible

    Yann Dirson (4):
          git-svn.txt: stop using dash-form of commands.
          git-svn.txt: make formatting more consistent.
          git-svn.txt: fix fetch flags incorrectly documented as init flags.
          git-svn.txt: fix description of fetch flags accepted by clone.

For example, you have this:

    commit eb0d671e3b73f05106dca83b9cecd74d4acdb291
    Author: Yann Dirson <ydirson@altern.org>
    Date:   Mon Jul 6 00:03:15 2009 +0200

which is an old iteration of 

    commit 6c32a7a99495da3f49e2a142791bc10af3f6f059
    Author: Yann Dirson <ydirson@altern.org>
    Date:   Tue Jul 7 22:22:20 2009 +0200

that is already in 'master'.

Perhaps you forgot to push it out?  These are what I see:

    $ git fetch git://git.bogomips.org/git-svn HEAD
    $ git log --oneline ..FETCH_HEAD
    6bb8ed9 git-svn: Fix branch detection when repository root is inaccessible
    2d4b387 git-svn: Always duplicate paths returned from get_log
    bca5572 git-svn.txt: fix description of fetch flags accepted by clone.
    e594175 git-svn.txt: fix fetch flags incorrectly documented as init flags.
    eb0d671 git-svn.txt: make formatting more consistent.
    6478d74 git-svn.txt: stop using dash-form of commands.

  reply	other threads:[~2009-07-12 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 22:53 git-svn is "Unable to determine upstream SVN information..." esskov
2009-07-10  3:31 ` Eric Wong
2009-07-10 11:15   ` Esben Skovenborg
2009-07-10 20:33     ` Eric Wong
2009-07-12 18:58       ` [PATCH] git svn: allow uppercase UUIDs from SVN Eric Wong
2009-07-12 21:15         ` Junio C Hamano
2009-07-12 21:53           ` Junio C Hamano [this message]
2009-07-12 21:56             ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7v7hydlgal.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=esskov@oncable.dk \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox