git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes
Date: Wed, 20 Apr 2005 23:03:30 +0200	[thread overview]
Message-ID: <20050420210330.GD19112@pasky.ji.cz> (raw)
In-Reply-To: <20050420205633.GC19112@pasky.ji.cz>

Dear diary, on Wed, Apr 20, 2005 at 10:56:33PM CEST, I got a letter
where Petr Baudis <pasky@ucw.cz> told me that...
>   cg pull will now always only pull, never merge.
> 
>   cg update will do pull + merge.

Note that what you will probably do _most_ by far is cg update.
You generally do cg pull only when you want to make sure you have the
latest and greatest when doing some cg diff or whatever, or on your
notebook when getting on an airplane. And you do direct cg merge generally
only on the airplane.

I also forgot one last usage change:

  cg fork BNAME BRANCH_DIR [COMMIT_ID]
  ->
  cg fork BRANCH_DIR [BNAME] [COMMIT_ID]

This will bring its usage in sync to both cg export and cg tag.
The branch name will also default to the last element in the
BRANCH_DIR path (that annoyed me a lot, basically writing a thing
two times at single line).

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

  reply	other threads:[~2005-04-20 20:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 20:56 [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Petr Baudis
2005-04-20 21:03 ` Petr Baudis [this message]
2005-04-20 21:19 ` Greg KH
2005-04-20 21:51   ` Mike Taht
2005-04-20 21:58     ` Joshua T. Corbin
2005-04-20 21:51   ` Petr Baudis
2005-04-20 21:54     ` Randy.Dunlap
2005-04-20 22:07       ` Steven Cole
2005-04-20 22:09     ` Linus Torvalds
2005-04-20 22:28       ` Petr Baudis
2005-04-20 23:04         ` Greg KH
2005-04-21  0:14         ` Linus Torvalds
2005-04-21  1:12           ` Linus Torvalds
2005-04-21  3:35             ` Daniel Jacobowitz
2005-04-21  2:45               ` Sean
2005-04-21  4:00               ` Linus Torvalds
2005-04-21  4:22                 ` Dave Jones
2005-04-21  5:08                   ` Junio C Hamano
2005-04-21  4:28                 ` Daniel Jacobowitz
2005-04-21  6:49                   ` Petr Baudis
2005-04-21 14:21                     ` Edgar Toernig
2005-04-21 16:42                       ` Petr Baudis
2005-04-24  0:09                     ` Paul Jackson
2005-04-21  5:14                 ` Randy.Dunlap
2005-04-21  4:27                   ` Sean
2005-04-21  5:29             ` Greg KH
2005-04-24  0:12             ` Paul Jackson
2005-04-21  2:48       ` Matthias Urlichs
2005-04-21 18:15         ` Removing command dispatcher (was Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes) David A. Wheeler
2005-04-21  7:49       ` [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Ingo Molnar
2005-04-25 11:27       ` Andrew Morton
2005-04-21  2:53 ` Bryan Donlan
2005-04-21  7:36   ` 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=20050420210330.GD19112@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --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.
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).