git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Marking abandoned branches
Date: Wed, 13 Sep 2006 11:59:53 -0400	[thread overview]
Message-ID: <9e4733910609130859v347a7a9ew5c3ebc982bf9b07b@mail.gmail.com> (raw)
In-Reply-To: <20060913152451.GH23891@pasky.or.cz>

On 9/13/06, Petr Baudis <pasky@suse.cz> wrote:
> Dear diary, on Wed, Sep 13, 2006 at 05:17:59PM CEST, I got a letter
> where Jon Smirl <jonsmirl@gmail.com> said that...
> > Abandoned branches are common in CVS since it is not distributed.
> > People start working on something in the main repo and then decide it
> > was a bad idea. In the git world these branches usually don't end up
> > in the main repo.
>
> Can't you just toss the branch away in that case? :-)

It is a historical import. Everything that was in the initial repo
needs to be preserved otherwise they aren't going to get rid of the
old CVS repo.

> You could also stash the ref to refs/heads-abandoned/ instead of
> refs/heads/ if you want to keep the junk around for some reason. Of
> course you don't get the nice marker with explanation of why is this
> abandoned and who decided that, but you can just use an empty commit for
> the same purpose.
>
> Object classes are precious things and we shouldn't get carried away.

If this is done with an object there should probably be some way to
encode it into the existing commit object.

Moving the refs into refs/abandoned would work too. We would need new
git commands to do this and flags on the visualization tools to
include the abandoned branches. On the other hand doing this is
recording state about the repository in the refs directory instead of
writing this state into the repo itself.

-- 
Jon Smirl
jonsmirl@gmail.com

  parent reply	other threads:[~2006-09-13 16:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 15:17 Marking abandoned branches Jon Smirl
2006-09-13 15:24 ` Petr Baudis
2006-09-13 15:31   ` Johannes Schindelin
2006-09-13 15:45     ` Jakub Narebski
2006-09-13 18:40     ` Junio C Hamano
2006-09-13 18:51       ` Jakub Narebski
2006-09-13 19:00         ` Junio C Hamano
2006-09-13 19:34           ` Jakub Narebski
2006-09-13 20:43             ` Petr Baudis
2006-09-13 20:45             ` Junio C Hamano
2006-09-13 21:02               ` Jakub Narebski
2006-09-13 21:09               ` Jakub Narebski
2006-09-13 21:32               ` Jakub Narebski
2006-09-13 15:59   ` Jon Smirl [this message]
2006-09-13 16:05     ` Johannes Schindelin
2006-09-13 17:22       ` Jon Smirl
2006-09-13 17:32         ` Shawn Pearce
2006-09-13 17:46         ` Nicolas Pitre
2006-09-13 20:31         ` Martin Langhoff
2006-09-13 20:43           ` Jakub Narebski
2006-09-13 16:09     ` Shawn Pearce
2006-09-13 16:12     ` Jakub Narebski
2006-09-13 16:40       ` A Large Angry SCM
2006-09-13 16:49         ` Shawn Pearce
2006-09-13 18:58           ` Junio C Hamano
2006-09-13 16:55         ` Jakub Narebski
2006-09-13 17:24           ` Jon Smirl
2006-09-13 17:45             ` Jakub Narebski
2006-09-14  3:37     ` Sam Vilain

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e4733910609130859v347a7a9ew5c3ebc982bf9b07b@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).