ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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 14:51:12 +0200	[thread overview]
Message-ID: <4A816940.20007@wxs.nl> (raw)
In-Reply-To: <20090811121513.GC20017@katherina.student.utwente.nl>

Matthijs Kooijman wrote:
> Hi Patrick,
> 
>> I don't know if you have noticed that the git repository has been
>> replaced by a newer one.
> 
> I'm surprised that there is even a git repository at all. On the wiki and all
> documents I've seen so far, there is only talk about rsyncing from an ftp, git
> is never mentioned.

these are different things:

- zips from www.pragma-ade.com: the official alpha, beta and current in 
tds format
- svn on tex.aanhet.net and gforge: the zips submitted in an svn repos
- ftp on one of our machines: intermediate versions for the happy few 
(non public)
- git on the garden: an experiment that started last context meeting and 
will launch upcoming context meeting
- minimals: stand alone tex installations efficiently synced with rsync

> However, looking at the contents of the git repository, it seems that this is
> just a repository that automatically checks the files from the ftp every so
> often? I was hoping for an actual git repository with commit messages to show
> changes, but it seems the git repository isn't the primary version of context

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

> (I guess Hans' local copy is)?

the zips are built from my local dev tree which has a completely 
different structure; reorganizing that all (sources, examples, manuals, 
presentations, etc etc) would cost me a lot of time (as not all is 
suitable for a repos), gains me nothing, and is no fun doing

if some huge project was paying for the effort i would consider doing it 
but at the moment it simply does not pay off

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
___________________________________________________________________________________


  reply	other threads:[~2009-08-11 12:51 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 [this message]
2009-08-11 13:42     ` Matthijs Kooijman
2009-08-11 14:25       ` Hans Hagen

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=4A816940.20007@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).