From: Jeff King <peff@peff.net>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jay Soffian <jaysoffian@gmail.com>,
Marc Branchaud <marcnarc@xiplink.com>,
Miles Bader <miles@gnu.org>,
git@vger.kernel.org
Subject: Re: setting up tracking on push
Date: Wed, 11 Mar 2009 12:40:30 -0400 [thread overview]
Message-ID: <20090311164030.GA5977@sigill.intra.peff.net> (raw)
In-Reply-To: <20090311190207.6117@nanako3.lavabit.com>
On Wed, Mar 11, 2009 at 07:02:07PM +0900, Nanako Shiraishi wrote:
> I'm sorry, but I don't understand why you want to keep the entries in
> the reflog that were made before you pushed your branch to make it
> public in this scenario.
>
> Especially because you are relinquishing the authority to the public
> repository by wishing to be able to "track" it, you can't rewind the
> branch beyond the point you initially pushed out any more. At that
> point, wouldn't it make more sense to drop the old reflog data and
> pretend as if the branch were fetched from the branch from your public
> repository it now follows, just like everybody else does?
That only means that you cannot rewind back to some spot in the reflog.
There is nothing to say that you cannot pull useful ideas from the
reflog that you thought were failed experiments, and apply them as
new commits.
-Peff
next prev parent reply other threads:[~2009-03-11 16:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 3:07 setting up tracking on push Miles Bader
2009-03-06 3:17 ` John Tapsell
2009-03-06 4:49 ` Jay Soffian
2009-03-06 10:45 ` Johannes Schindelin
2009-03-06 11:15 ` Miles Bader
2009-03-06 14:15 ` Jeremy O'Brien
2009-03-06 15:43 ` Jay Soffian
2009-03-06 16:29 ` Miles Bader
2009-03-10 20:26 ` Marc Branchaud
2009-03-10 23:09 ` Jeff King
2009-03-11 1:52 ` Jay Soffian
2009-03-11 2:04 ` Jeff King
2009-03-11 2:59 ` Jay Soffian
2009-03-11 3:06 ` Jeff King
2009-03-11 3:40 ` Jay Soffian
2009-03-11 3:44 ` Jay Soffian
2009-03-11 3:57 ` Jeff King
2009-03-11 4:15 ` Jay Soffian
2009-03-24 9:58 ` Jakub Narebski
2009-03-11 4:37 ` Junio C Hamano
2009-03-11 4:56 ` Miles Bader
2009-03-11 5:03 ` Miles Bader
2009-03-11 5:22 ` Jay Soffian
2009-03-11 21:39 ` Marc Branchaud
2009-03-11 6:32 ` Jeff King
2009-03-11 10:02 ` Nanako Shiraishi
2009-03-11 16:40 ` Jeff King [this message]
2009-03-12 0:08 ` John M. Dlugosz
2009-03-12 0:58 ` Jay Soffian
2009-03-12 1:11 ` Junio C Hamano
2009-03-12 1:16 ` Jay Soffian
2009-03-12 1:14 ` Jay Soffian
2009-03-12 1:21 ` Jay Soffian
2009-03-15 3:28 ` John M. Dlugosz
2009-03-15 12:36 ` Jay Soffian
2009-03-16 1:07 ` John M. Dlugosz
2009-03-16 1:43 ` Jay Soffian
2009-03-15 18:33 ` Junio C Hamano
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=20090311164030.GA5977@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=marcnarc@xiplink.com \
--cc=miles@gnu.org \
--cc=nanako3@lavabit.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).