From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: make[1]: *** [gnus-load.el] Erreur 2
Date: Mon, 04 Oct 2010 15:27:50 -0500 [thread overview]
Message-ID: <8762xhd7p5.fsf@lifelogs.com> (raw)
In-Reply-To: <87zkut94cb.fsf@sphax.lybrafox.lan>
On Mon, 04 Oct 2010 20:53:55 +0200 hobbes@poukram.net (Rémi Letot) wrote:
RL> As I'm new to git, I don't know if "git pull" is enough to get the
RL> latest developments, so I cloned a fresh full copy and got the same
RL> result.
`git pull' will get you the latest unless your local copy has
modifications. Then you need to merge (I usually save to the stash,
pull, then pop the stash to preserve experimental changes).
To be sure, do `git log' to see the last change and `git st' to check
you don't have local modifications.
Ted
prev parent reply other threads:[~2010-10-04 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 18:53 Rémi Letot
2010-10-04 19:06 ` Lars Magne Ingebrigtsen
2010-10-04 19:23 ` Rémi Letot
2010-10-04 19:28 ` Lars Magne Ingebrigtsen
2010-10-04 19:38 ` Rémi Letot
2010-10-04 20:01 ` Adam Sjøgren
2010-10-04 20:20 ` Rémi Letot
2010-10-04 20:35 ` Adam Sjøgren
2010-10-04 20:31 ` Romain Francoise
2010-10-04 20:43 ` Rémi Letot
2010-10-04 20:57 ` Rémi Letot
2010-10-04 20:56 ` Andreas Schwab
2010-10-04 20:27 ` Ted Zlatanov [this message]
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=8762xhd7p5.fsf@lifelogs.com \
--to=tzz@lifelogs.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).