git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jan Hudec <bulb@ucw.cz>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jonathan Watt <jwatt@jwatt.org>, Elijah Newren <newren@gmail.com>,
	git@vger.kernel.org
Subject: Re: Auto detaching head options (update) (Re: Working copy revision and push pain)
Date: Sun, 30 Mar 2008 22:09:21 -0400	[thread overview]
Message-ID: <20080331020920.GA412@coredump.intra.peff.net> (raw)
In-Reply-To: <20080331015937.GA32645@coredump.intra.peff.net>

On Sun, Mar 30, 2008 at 09:59:37PM -0400, Jeff King wrote:

> Why is 605fac8 beneficial? What common workflow is updating the HEAD
> branch through its actual name? If it is manipulating the index and

Apparently my reading skills are not what they used to be. In the
comment from 605fac8, it specifically mentions pushing directly into a
branch that is the same as HEAD. But that is one of the cases that we
Jan is trying to improve, so I don't see a problem with reverting in
favor of his proposal.

-Peff

  reply	other threads:[~2008-03-31  2:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 12:39 Working copy revision and push pain Jonathan Watt
2008-03-23 13:02 ` Johannes Schindelin
2008-03-23 13:19   ` Jonathan Watt
2008-03-23 13:45     ` Elijah Newren
2008-03-23 13:54       ` Jonathan Watt
2008-03-23 14:06         ` Elijah Newren
2008-03-23 14:22           ` Johannes Schindelin
2008-03-23 14:48             ` Jonathan Watt
2008-03-23 14:56               ` Johannes Schindelin
2008-03-23 15:25                 ` Jonathan Watt
2008-03-23 16:00                   ` Johannes Schindelin
2008-03-25 19:25                     ` Auto detaching head options (Re: Working copy revision and push pain) Jan Hudec
2008-03-25 19:58                       ` Johannes Schindelin
2008-03-25 23:24                       ` Jeff King
2008-03-26 18:49                         ` Junio C Hamano
2008-03-29  8:27                           ` Auto detaching head options (update) " Jan Hudec
2008-03-29  8:47                             ` Jeff King
2008-03-31  1:53                               ` Junio C Hamano
2008-03-31  1:59                                 ` Jeff King
2008-03-31  2:09                                   ` Jeff King [this message]
2008-03-23 19:48             ` Working copy revision and push pain Elijah Newren
2008-03-23 14:27           ` Jonathan Watt
2008-03-23 14:34             ` Johannes Schindelin
2008-03-23 16:20               ` Johan Herland
2008-03-23 17:24                 ` Jonathan Watt
2008-03-23 18:21                   ` Junio C Hamano
2008-03-23 19:42                     ` Junio C Hamano
2008-03-23 18:23                   ` Johannes Schindelin
2008-03-24 15:22                 ` Johannes Schindelin
2008-03-24 18:00                   ` Johan Herland
2008-03-23 14:11     ` Johannes Schindelin
2008-03-23 14:35       ` Jonathan Watt

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=20080331020920.GA412@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jwatt@jwatt.org \
    --cc=newren@gmail.com \
    /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).