git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Check for IO errors after running a command
Date: Mon, 25 Jun 2007 15:42:04 +0200	[thread overview]
Message-ID: <467FC62C.87F83541@eudaptics.com> (raw)
In-Reply-To: Pine.LNX.4.64.0706251413530.4059@racer.site

Johannes Schindelin wrote:
> One thing we might consider, however: when rebasing, the current branch
> gets updated at each step. Some might consider this a bug, and prefer
> rebase to work on a detached HEAD, and only update the branch at the end,
> so that <branchname>@{1} refers to the state _before_ rebase.

YESSSS!

Finding the commit before the rebase in the reflog is a nightmare.

-- Hannes

  reply	other threads:[~2007-06-25 13:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23 15:13 (resend) [PATCH] Don't ignore write failure from git-diff, git-log, etc Jim Meyering
2007-06-24  9:01 ` Junio C Hamano
2007-06-24 17:08   ` Linus Torvalds
2007-06-24 17:10     ` [PATCH 1/2] Clean up internal command handling Linus Torvalds
2007-06-24 17:29     ` [PATCH 2/2] Check for IO errors after running a command Linus Torvalds
2007-06-25  9:44       ` Junio C Hamano
2007-06-25 13:20         ` Johannes Schindelin
2007-06-25 13:42           ` Johannes Sixt [this message]
2007-06-25 14:01         ` Jim Meyering
2007-06-25 15:57           ` Linus Torvalds
2007-06-26 13:33         ` Matthias Lederhofer
2007-06-25 19:54       ` Jim Meyering
2007-06-24 19:13     ` (resend) [PATCH] Don't ignore write failure from git-diff, git-log, etc Jim Meyering

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=467FC62C.87F83541@eudaptics.com \
    --to=j.sixt@eudaptics.com \
    --cc=git@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).