From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Ma Gnus v0.1 is released
Date: Wed, 01 Feb 2012 08:04:57 -0500 [thread overview]
Message-ID: <87mx92puva.fsf@newsguy.com> (raw)
In-Reply-To: <87ty3bbyh5.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> git clone http://git.gnus.org/gnus.git && cd gnus && git checkout m0-1
Just making sure about something.... No git skills at all so:
First I rename the existing `gnus' to gnus_old then:
Once the commands above have been done...
how would a user keep up with development...?
`cd gnus; git pull'
Does not do like it used to, once the clone command has been run.
for example, in the `gnus' directory created by the `git clone [...]'
cmd above (from inside the gnus directory):
If I run `git pull' I get this error
WARNING: gnome-keyring:: no socket to connect to
You are not currently on a branch, so I cannot use any
'branch.<branchname>.merge' in your configuration file.
Please specify which branch you want to merge with on the command
line and try again (e.g. 'git pull <repository> <refspec>').
See git-pull(1) for details.
But if I move to the old gnus directory now named gnus_old:
cd ../gnus_old, here `git pull' works as expected
git pull
WARNING: gnome-keyring:: no socket to connect to
Already up-to-date.
next prev parent reply other threads:[~2012-02-01 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:59 Lars Ingebrigtsen
2012-01-31 17:10 ` Richard Riley
2012-02-01 1:17 ` Yagnesh Raghava Yakkala
2012-02-01 4:57 ` Richard Riley
2012-02-01 6:26 ` Yagnesh Raghava Yakkala
2012-02-01 18:13 ` Ted Zlatanov
2012-02-01 22:02 ` Steinar Bang
2012-01-31 17:38 ` Frank Haun
2012-02-01 13:04 ` Harry Putnam [this message]
2012-02-01 13:36 ` Steinar Bang
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=87mx92puva.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=ding@gnus.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).