git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Re: Re: Add "clone" support to lntree
Date: Tue, 19 Apr 2005 03:12:07 +0200
Message-ID: <20050419011206.GT5554@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0504161951160.30848-100000@iabervon.org>

For the record, mostly... (this is how it already is in git-pasky-0.5)

Dear diary, on Sun, Apr 17, 2005 at 02:07:36AM CEST, I got a letter
where Daniel Barkalow <barkalow@iabervon.org> told me that...
> > Now, what about git branch and git update for switching between
> > branches? I think this is the most controversial part; these are
> > basically just shortcuts for not having to do git fork, and I wouldn't
> > mind so much removing them, if you people really consider them too ugly
> > a wart for the soft clean git skin. I admit that they both come from a
> > hidden prejudice that git fork is going to be slow and eat a lot of
> > disk.
> 
> I think that this just confuses matters.

I killed them both for good.

> > The idea for git update for switching between branches is that
> > especially when you have two rather similar branches and mostly do stuff
> > on one of them, but sometimes you want to do something on the other one,
> > you can do just quick git update, do stuff, and git update back, without
> > any forking.
> 
> I still think that fork should be quick enough, or you could leave the
> extra tree around. I'm not against having such a command, but I think it
> should be a separate command rather than a different use of update, since
> it would be used by poeople working in different ways.

I've removed git branch, removed the possibility for git update to
switch branches and renamed git update to git seek. You can do

	git seek git-pasky-0.1

and examine stuff, but your tree is also blocked at the same time - git
won't let you commit, merge and such. By doing

	git seek
or
	git seek master

you return back to your branch (assuming its name is master).

I think git fork is after all good enough for branching and it is the
clean way. Shall there be a big demand for it, it should be minimal
hassle to implement 'git switch', which would do that.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

  reply index

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16  1:56 [PATCH] " Daniel Barkalow
2005-04-16  2:47 ` Petr Baudis
2005-04-16  2:58   ` Petr Baudis
2005-04-16  3:16     ` Linus Torvalds
2005-04-16 11:39       ` Petr Baudis
2005-04-16  3:17     ` Daniel Barkalow
2005-04-16 23:33       ` Petr Baudis
2005-04-17  0:07         ` Daniel Barkalow
2005-04-19  1:12           ` Petr Baudis [this message]
2005-04-19  2:13             ` Change "pull" to _only_ download, and "git update"=pull+merge? David A. Wheeler
2005-04-19  9:18               ` David Greaves
2005-04-19  9:28                 ` Petr Baudis
2005-04-19 10:05                   ` Martin Schlemmer
2005-04-19 10:50                     ` Petr Baudis
2005-04-19 13:54                       ` Jon Seymour
2005-04-19 14:40                       ` Martin Schlemmer
2005-04-19 18:28                       ` Daniel Barkalow
2005-04-19 22:39                         ` David A. Wheeler
2005-04-19 23:20                           ` Daniel Barkalow
2005-04-20  7:01                       ` Ingo Molnar
2005-04-20 20:05                         ` Petr Baudis
2005-04-20 20:32                           ` Ingo Molnar
2005-04-20 20:45                           ` Ingo Molnar
2005-04-20 21:15                             ` Petr Baudis
2005-04-20 23:58                               ` David Mansfield
2005-04-16  3:06   ` Add "clone" support to lntree Daniel Barkalow
2005-04-16 23:00     ` Petr Baudis
2005-04-16 23:07       ` Daniel Barkalow
2005-04-16 23:44         ` Petr Baudis

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=20050419011206.GT5554@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=barkalow@iabervon.org \
    --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

git@vger.kernel.org list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git