Git development
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Frank Sorenson <frank@tuxrocks.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How do I...
Date: Fri, 06 May 2005 09:37:01 -0500	[thread overview]
Message-ID: <1115390221.10459.4.camel@localhost> (raw)
In-Reply-To: <427B3DB3.4000507@tuxrocks.com>

On Fri, 2005-05-06 at 03:49 -0600, Frank Sorenson wrote:

> After doing a cg-update, can I cg-log just the changes since the last
> update?  Alternatively, how can I tell cg-log I'm caught up, and don't
> need anything historical?

(Assuming pulling from "origin")
Instead of doing cg-update, do cg-pull.  Then "cg-log :origin" will give
you you the changesets you just pulled.  "cg-merge origin" will then
complete operation, thereby catching you up.

-- 
David Kleikamp
IBM Linux Technology Center


  parent reply	other threads:[~2005-05-06 14:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  9:49 How do I Frank Sorenson
2005-05-06  9:59 ` Thomas Glanzmann
2005-05-06 10:03   ` Thomas Glanzmann
2005-05-06 14:37 ` Dave Kleikamp [this message]
2005-05-06 16:39   ` Frank Sorenson
2005-05-06 17:58     ` Dave Kleikamp
2005-05-06 19:07       ` Frank Sorenson
2005-05-06 16:13 ` Linus Torvalds
2005-05-06 16:35   ` Junio C Hamano
2005-05-06 16:47     ` Frank Sorenson
2005-05-06 17:31       ` Daniel Barkalow
2005-05-06 18:56         ` Frank Sorenson
2005-05-06 17:09     ` Linus Torvalds
2005-05-06 18:39       ` David Woodhouse
2005-05-06 18:59         ` Linus Torvalds
2005-05-06 19:10           ` David Woodhouse
2005-05-06 22:57             ` Linus Torvalds
2005-05-06 23:20               ` David Woodhouse
2005-05-06 23:54                 ` Linus Torvalds
2005-05-07  8:58                   ` David Woodhouse
2005-05-06 19:35           ` Thomas Kolejka
2005-05-06 16:36   ` David Woodhouse
2005-05-07  0:45     ` Benjamin Herrenschmidt
2005-05-06 18:58 ` Linus Torvalds

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=1115390221.10459.4.camel@localhost \
    --to=shaggy@austin.ibm.com \
    --cc=frank@tuxrocks.com \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox