Junio C Hamano wrote:
> But what does it have to do with rebase polluting the reflog?
See the series I just posted.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.
Ramkumar Ramachandra writes:
> Ramkumar Ramachandra wrote:
>> t/status-help. Looks seriously unrelated, and I'm breaking my head
>> over it. Any clues?
>
> Damn it! A recent commit is responsible for this avalanche in test
> breakages: b397ea (status: show more info than "currently not on any
Ramkumar Ramachandra wrote:
> t/status-help. Looks seriously unrelated, and I'm breaking my head
> over it. Any clues?
Damn it! A recent commit is responsible for this avalanche in test
breakages: b397ea (status: show more info than "currently not on any
branch", 2013-03-13). It re-implements
Junio C Hamano wrote:
> I am curious what breaks, though.
t/status-help. Looks seriously unrelated, and I'm breaking my head
over it. Any clues?
--- expected2013-06-10 17:16:42.276356867 +
+++ actual 2013-06-10 17:16:42.279690201 +
@@ -1,4 +1,4 @@
-# HEAD detached at 000106f
+#
Ramkumar Ramachandra writes:
> Invoking 'git rebase -i' writes the following line to the reflog at the
> start of the operation:
>
> rebase -i (start)
>
> This is not very useful. Make it more informative like:
>
> rebase -i (start): checkout master
Makes sense to me, at least within the sc
Invoking 'git rebase -i' writes the following line to the reflog at the
start of the operation:
rebase -i (start)
This is not very useful. Make it more informative like:
rebase -i (start): checkout master
Signed-off-by: Ramkumar Ramachandra
---
git-rebase--interactive.sh | 2 ++
1 file c
6 matches
Mail list logo
