Martin von Zweigbergk martinv...@gmail.com writes:
On Wed, Nov 23, 2011 at 10:51 AM, Junio C Hamano gits...@pobox.com wrote:
I am guilty of introducing git reset --soft HEAD^ before I invented
commit --amend during v1.3.0 timeframe to solve the issue soft reset
originally wanted to.
I do
On Mon, Dec 17, 2012 at 10:34:07PM -0800, Martin von Zweigbergk wrote:
On Wed, Nov 23, 2011 at 10:51 AM, Junio C Hamano gits...@pobox.com wrote:
I am guilty of introducing git reset --soft HEAD^ before I invented
commit --amend during v1.3.0 timeframe to solve the issue soft reset
On Wed, Nov 23, 2011 at 12:49 AM, Matthieu Moy
matthieu@grenoble-inp.fr wrote:
Philippe Vaucher philippe.vauc...@gmail.com writes:
Optional: a new mode would be introduced for consistency:
--worktree (or maybe --tree): only updates the worktree but not the index
That would be an alias
On Wed, Nov 23, 2011 at 10:51 AM, Junio C Hamano gits...@pobox.com wrote:
I am guilty of introducing git reset --soft HEAD^ before I invented
commit --amend during v1.3.0 timeframe to solve the issue soft reset
originally wanted to.
I do use commit --amend a lot, but I still appreciate having
On Wednesday 2012-10-03 21:03, Junio C Hamano wrote:
I said that git reset --keep started out as an ugly workaround for
the lack of git checkout -B $current_branch. Now we have it, so
we can afford to make reset --keep less prominently advertised in
our tool set. As I already said back then,
Phil Hord phil.h...@gmail.com writes:
I flagged this for followup in my MUA, but I failed to follow-up after
the holidays. I apologize for that, and I really regret it because I
liked where this was going.
I really regret to see you remembered it, actually.
1) Newbie user clones/pulls a
Junio C Hamano gits...@pobox.com writes:
Phil Hord phil.h...@gmail.com writes:
I flagged this for followup in my MUA, but I failed to follow-up after
the holidays. I apologize for that, and I really regret it because I
liked where this was going.
I really regret to see you remembered it,
7 matches
Mail list logo
