From: "Sean" <seanlkml@sympatico.ca>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: git@vger.kernel.org
Subject: Re: cogito - how do I ???
Date: Sat, 21 May 2005 18:06:04 -0400 (EDT) [thread overview]
Message-ID: <2765.10.10.10.24.1116713164.squirrel@linux1> (raw)
In-Reply-To: <20050521214700.GA18676@mars.ravnborg.org>
On Sat, May 21, 2005 5:47 pm, Sam Ravnborg said:
> Hi all.
>
> While trying to get up to speed on cogito/git I stumbled across
> a few things that I at least did not find available in cogito.
>
> 1) Something similar to "bk changes -R". I use this to see what has
> happened upstream - to see if I really want to merge stuff.
Not sure what bk did here, but you can do something like:
cg-pull origin
cg-log -c -r origin
To see what is at the head of the unmerged objects you just pulled down,
and if you want to merge then "cg-merge origin". Although as far as I
know there's no way to have the log stop automatically at the proper spot.
> 2) Export of individual patches. "bk export -tpatch -r1.2345"
> I have nu public git repository yet so I have to feed changes as
> plain patches. Browsing cg-* I did not find the command to do this.
cg-diff -p -r SHA1
Which asks for the diff from the parent (-p) to the revision (-r).
Sean
next prev parent reply other threads:[~2005-05-21 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 21:47 cogito - how do I ??? Sam Ravnborg
2005-05-21 22:06 ` Sean [this message]
2005-05-21 23:41 ` Linus Torvalds
2005-05-22 7:14 ` Sam Ravnborg
2005-05-22 16:23 ` Linus Torvalds
2005-05-23 7:19 ` Thomas Glanzmann
2005-05-23 7:40 ` Junio C Hamano
2005-05-23 8:02 ` Thomas Glanzmann
2005-05-23 14:35 ` Linus Torvalds
2005-05-23 16:34 ` Junio C Hamano
2005-05-24 2:26 ` Herbert Xu
2005-05-24 3:05 ` Linus Torvalds
2005-05-22 5:27 ` Frank Sorenson
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=2765.10.10.10.24.1116713164.squirrel@linux1 \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=sam@ravnborg.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).