From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: git repository
Date: Tue, 11 Aug 2009 16:25:06 +0200 [thread overview]
Message-ID: <4A817F42.1050201@wxs.nl> (raw)
In-Reply-To: <20090811134205.GF20017@katherina.student.utwente.nl>
Matthijs Kooijman wrote:
>> well, such messages would not help much unless they would be detailed
>> (and then should be done for each file); as i work on all files at the
>> same time it would cost me way to much time and it gains me nothing;
>> looking at the diff in a git gui is more informative
> A git commit contains changes to multiple files, with a single message, so if
> you work on one logical change at a time, this should not be a problem.
> Perhaps you are thinking of CVS, which (AFAIK) provides only per-file
> versioning?
sure, but i never change 'one file' per commit, often many small changes
in files (even typos or just formatting)
> Also, even short messages like, "Added \foo command", or "Fixed \bar
> alignment" would probably be helpful.
i've probably forgotten that by the time i submit a zip as there can be
quit esome time between a commit then
> Then again, you are completely correct that there is some effort to be
> invested to properly use a versioning system, especially if you're not used to
> working with one. In my experience, having a versioning system like git (or
> mercurial seems to be good as well) does pay off in the long run, but only if
> you tune your development flow to work well with it.
indeed, and we started on context way before there was git (and many
files are involved, not only tex files); changing now would probably
stall me for a while
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-08-11 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 6:25 Patrick Gundlach
2009-08-11 12:15 ` Matthijs Kooijman
2009-08-11 12:51 ` Hans Hagen
2009-08-11 13:42 ` Matthijs Kooijman
2009-08-11 14:25 ` Hans Hagen [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=4A817F42.1050201@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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).