There is a useful convenience for synchronizing a local repository with
changes that have accumulated on the pull/push area: see "hg fetch" in the
Mercurial book http://hgbook.red-bean.com or the wiki.
The relevant section from the book is attached below.
The "fetch" command automatically handl
Tjark Weber wrote:
> On Tue, 2008-12-02 at 22:09 +0100, Makarius wrote:
>> With Mercurial you have the whole history always around, and there is no
>> need to encode (tiny) parts of it in the file.
>
> Certainly $Id$ keys are rather useless as long as the file is part of a
> managed repository.
On Wed, 3 Dec 2008, Gerwin Klein wrote:
> I'm no great friend of $Id$, but Tjark does have a point: we release
> development snapshots and it is very easy to confuse versions when
> people ask questions about specific files etc.
People should be able to say which release they are using. For th
On Tue, 2 Dec 2008, Tjark Weber wrote:
> On Tue, 2008-12-02 at 22:09 +0100, Makarius wrote:
> > With Mercurial you have the whole history always around, and there is no
> > need to encode (tiny) parts of it in the file.
>
> Certainly $Id$ keys are rather useless as long as the file is part of a
On Tue, 2008-12-02 at 22:09 +0100, Makarius wrote:
> With Mercurial you have the whole history always around, and there is no
> need to encode (tiny) parts of it in the file.
Certainly $Id$ keys are rather useless as long as the file is part of a
managed repository. However, files escape into th
One more general note getting started with Mercurial: When exploring
features of the system, please do it privately, on smaller repositories
first!
The Isabelle repository is very complex and many other people depend on it
working smoothly. Anything that might end up in the central place shoul
On Tue, 2 Dec 2008, Tjark Weber wrote:
> One can argue that such keys are not necessary (since files in the
> repository can be identified by their changeset id); however, this is
> true only as long as one knows where a file is coming from.
>
> If you want keyword expansion, instructions can be
On Sun, 30 Nov 2008, Makarius wrote:
> After several months of getting acquainted with "distributed version
> control" in general, we should be finally ready to switch the official
> Isabelle repository to Mercurial.
I noticed that Mercurial does not perform CVS keyword expansion by
default, cau
A few more tips on getting started in a safe way, and avoiding surprises:
* Use "hg outgoing" to see beforehand what "hg push" would do; the same
works for "hg incoming" and "hg pull".
There is a real danger of messing up our central push area by merging
it with my earlier attemp
On Sun, 30 Nov 2008, Makarius wrote:
> After several months of getting acquainted with "distributed version
> control" in general, we should be finally ready to switch the official
> Isabelle repository to Mercurial.
> After pressing the red button, the conversion job will be stopped and
> pus
After several months of getting acquainted with "distributed version
control" in general, we should be finally ready to switch the official
Isabelle repository to Mercurial.
In fact, http://isabelle.in.tum.de/repos/isabelle has been around in the
present form for several weeks already. It can
11 matches
Mail list logo
