From: Junio C Hamano <gitster@pobox.com>
To: "David Jeske" <jeske@willowmail.com>
Cc: "Theodore Tso" <tytso@mit.edu>, git@vger.kernel.org
Subject: Re: policy and mechanism for less-connected clients
Date: Wed, 25 Jun 2008 15:13:15 -0700 [thread overview]
Message-ID: <7viqvxxix0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1784.50359167091$1214430241@news.gmane.org> (David Jeske's message of "Wed, 25 Jun 2008 21:34:16 -0000")
"David Jeske" <jeske@willowmail.com> writes:
>> : "ncvs up" ->
>> :
>> : git stash; git pull; git apply;
First of all, if you are in CVS mindset, you may not want to necessarily
do "git pull", but "git fetch" followed by "git rebase".
I suspect the last one in the above sequence of yours is "git stash pop".
Definitely not "git apply" without any argument which is a no-op.
>> : git diff --stat <baseof:current branch> - un-pushed filenames
"git diff [--options] origin..." (three-dots) is often used. This is a
shorthand for:
git diff [--options] $(git merge-base origin HEAD) HEAD
that is, "show me what I did since I forked from origin".
>> : git-show-branch <current branch> - un-pushed comments
This would be useful if you are using "fetch + rebase", but in any case
git log --graph --pretty=oneline origin..
may be prettier these days. --graph is a recent invention that appeared
first in 1.5.6.
> Question: How do I create a branch on a remote repo when I'm on
> my local machine, without sshing to it?
I hope that the question is not "How do I do anything on a remote without
having any network connection to it" as its answer cannot be anything but
"telepathy".
next prev parent reply other threads:[~2008-06-25 22:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 13:34 policy and mechanism for less-connected clients Theodore Tso
2008-06-25 17:34 ` Junio C Hamano
[not found] ` <willow-jeske-01l6@3PlFEDjCVAh-01l6OB5yFEDjCYe3>
2008-06-25 19:37 ` David Jeske
[not found] ` <willow-jeske-01l6@3PlFEDjCVAh-01l6XqjPFEDjCY6P>
2008-06-25 21:34 ` David Jeske
2008-06-25 22:10 ` Jakub Narebski
2008-06-25 22:13 ` Junio C Hamano [this message]
[not found] ` <willow-jeske-01l6@3PlFEDjCVAh-01l6[3InFEDjC[dy>
2008-06-25 23:03 ` David Jeske
2008-06-25 23:03 ` David Jeske
2008-06-25 21:34 ` David Jeske
2008-06-25 19:37 ` David Jeske
2008-06-25 20:52 ` Jakub Narebski
2008-06-25 20:54 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 11:37 Theodore Tso
[not found] ` <willow-jeske-01l6@3PlFEDjCVAh-01l6rSE7FEDjCYv6>
2008-06-26 16:21 ` David Jeske
2008-06-26 16:21 ` David Jeske
2008-06-26 5:23 Theodore Tso
2008-06-26 5:26 ` Junio C Hamano
[not found] ` <willow-jeske-01l6@3PlFEDjCVAh-01l6it3ZFEDjCd5X>
2008-06-26 6:08 ` David Jeske
2008-06-26 6:08 ` David Jeske
2008-06-25 14:03 Petr Baudis
2008-06-25 2:33 Theodore Tso
[not found] ` <willow-jeske-01l6@3PlFEDjCVAh-01l6@3N@FEDjCXZO>
2008-06-25 5:20 ` David Jeske
2008-06-25 9:30 ` Jakub Narebski
2008-06-25 5:20 ` David Jeske
2008-06-25 19:17 ` Daniel Barkalow
2008-06-25 20:12 ` Raimund Bauer
2008-06-25 0:36 David Jeske
2008-06-25 0:36 David Jeske
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=7viqvxxix0.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jeske@willowmail.com \
--cc=tytso@mit.edu \
/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).