Re: [PATCH 1/3] t9350: point out that refs are not updated correctly
- From
Sverre Rabbelier <srabbelier@gmail.com>
- Date
- Oct 25, 2012, 05:39 UTC
- Message-ID
- <CAGdFq_gg3gPvCADje9ibz8xHgPOLF+=79EqksVzG2JeTOfHocw@mail.gmail.com>
- In-Reply-To
- <20121025052823.GB11243@elie.Belkin>
On Wed, Oct 24, 2012 at 10:28 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 5 quoted lines
> The testcase is imho correct and does not need changing. So yes, I > don't want your help changing it. I don't suspect you will be using > "git fast-export $(git rev-parse master)..master". It is safe and > good to add additional testcases documenting the syntax that you do > use, as an independent topic.
To re-iterate Dscho's point, the reason for this testcase is that if you do this: $ git checkout master $ git branch next $ git push hg://example.com master $ git push hg://example.com next
With the current design, next will not be present on the remote. This is caused by the fact that git looks at "fast-export ^master next", sees that it's empty, and decides not to export anything. This patch series solves that, by having "fast-export ^master next" emit a "from :42\nreset next" (or something like that, assuming :42 is where master is currently at).
-- Cheers, Sverre Rabbelier