From: Andreas Ericsson <ae@op5.se>
To: "MichaelTiloDressel@t-online.de" <MichaelTiloDressel@t-online.de>
Cc: git@vger.kernel.org
Subject: Re: cogito remote branch
Date: Fri, 09 Nov 2007 14:20:05 +0100 [thread overview]
Message-ID: <47345E85.8090702@op5.se> (raw)
In-Reply-To: <1IqTj5-24rt3I0@fwd33.aul.t-online.de>
MichaelTiloDressel@t-online.de wrote:
> Hi,
>
> I just saw the scripts cg-update, cg-push .. scripts try to guess a
> branch name functioning as origin if no argument is given. These scripts
> seam to use a branch named <branchname>-origin if it exists and the
> current
> branch is named <branchname> and is not the branch named master.
>
> I like that feature. Is it anywhere documented?
>
> In case there is no branch named <branchname>-origin the scripts just
> use origin even if the current branch is not master. I would prefer the
> scripts to fail in this case and to print a message asking the user to
> specifically name a branch.
>
Cogito is deprecated, and has been for quite some time. The "remote"
feature of core git (inspired by cogito) offers similar benefits.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-11-09 13:20 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 [this message]
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
-- 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=47345E85.8090702@op5.se \
--to=ae@op5.se \
--cc=MichaelTiloDressel@t-online.de \
--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;
as well as URLs for NNTP newsgroup(s).