From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: cogito remote branch
Date: Sat, 10 Nov 2007 12:52:39 +0100 [thread overview]
Message-ID: <fh4627$men$1@ger.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0711101217130.4330@castor.milkiway.cos
Michael Dressel wrote:
> On Fri, 9 Nov 2007, Jon Loeliger wrote:
>> On Fri, 2007-11-09 at 10:10, MichaelTiloDressel@t-online.de wrote:
>>
>>> There are just some features
>>> which simplify things for me in cogito. E.g. in cogito in the simplest
>>> way you don't need to be aware of the index. While with git
>>> you have to remember to add the changes to the index explicitly
>>> to get them committed.
>>
>> "git commit -a ..." might be useful for you.
>>
>> Other lingering cogito-isms you think are lacking in git?
>
> Thanks for the hint. I have to use git for a while to understand what may
> still be lacking (at least for me, if at all). Off the top of my head one
> other difference is that if I do a cg-push the remote (or origin) head is
> updated automatically, I think.
If you mean that tracking branches are updated on push, this is what
git also does from some time (perhaps not in released version, so please
wait or run 'master').
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-11-10 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 13:16 cogito remote branch MichaelTiloDressel
2007-11-09 13:20 ` Andreas Ericsson
2007-11-09 13:51 ` MichaelTiloDressel
2007-11-09 14:17 ` Johannes Schindelin
2007-11-09 16:10 ` MichaelTiloDressel
2007-11-09 16:28 ` Jon Loeliger
2007-11-10 11:27 ` Michael Dressel
2007-11-10 11:52 ` Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-10 12:35 Michael Dressel
2007-11-11 13:08 (unknown) Michael Dressel
2007-11-11 15:22 ` (no subject) Johannes Schindelin
2007-11-12 8:00 ` cogito remote branch MichaelTiloDressel
2007-11-12 9:55 ` Johannes Schindelin
2007-11-12 10:47 ` MichaelTiloDressel
2007-11-11 13:11 Michael Dressel
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='fh4627$men$1@ger.gmane.org' \
--to=jnareb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.