Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #32257
| From | Martin Gregorie <martin@address-in-sig.invalid> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Source Management |
| Date | 2015-08-04 09:15 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <mppvrn$qhi$1@dont-email.me> (permalink) |
| References | <d3240fa5-2144-4dee-8249-62882bd6b02d@googlegroups.com> <mpoja7$t7e$1@dont-email.me> |
On Mon, 03 Aug 2015 21:36:55 +0100, Eternal Hope wrote: > On 03/08/2015 16:00, e.d.programmer@gmail.com wrote: >> There was another thread discussing Sourceforge and github which was >> off topic so I started a new thread. >> What is a good offline source management software? We're using >> SourceTree but either it needs a lot of configuration we can't figure >> out or it just plain sucks. > > Well it might suck, or it might not depending on your point of view but > I'm pretty sure you can do anything you need to with git, after all, > it's the tool used to manage the Linux kernel source and there are > probably dozens if not hundreds of contributors to that. > > I can't say I've found the canonical git documentation. > This link https://progit.org/ points to the docs I'm currently using. I > only use the Linux terminal CLI I have to admit, fancy GUI interfaces > don't *always* make things clearer/easier to use, at least not for me. I suppose the mother lode is "Pro Git" by Scott Chacon and Ben Straub. Its downloadable from http://git-scm.com/book/en/v2 as PDF, mobi or epub, is readable as HTML from that URL. Or you can buy a paper copy. I thought that was overkill but like dead-tree reference material, so I bought the "GIT Pocket Guide" by Richard Silverman, an O'Reilly book. As a user guide its fine except for one point that rather screwed me up when I set up my first git repository for a pre-existing source tree: the "Ignoring files" section on page 42 should be at the end of page 38, because you need to tell git which files to ignore *before* you create the empty repository. If you do things in the order given in the book you find you've sucked files you'd want to ignore, such as *.class files, into the repository before setting up the to-be-ignored list. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Source Management e.d.programmer@gmail.com - 2015-08-03 08:00 -0700
Re: Source Management Cecil Westerhof <Cecil@decebal.nl> - 2015-08-03 18:04 +0200
Re: Source Management e.d.programmer@gmail.com - 2015-08-03 12:08 -0700
Re: Source Management leif.roar@dimnakorr.com - 2015-08-03 16:09 -0500
Re: Source Management Eternal Hope <laughingspam99@gmail.com> - 2015-08-03 21:36 +0100
Re: Source Management Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-04 09:15 +0000
Re: Source Management Eternal Hope <laughingspam99@gmail.com> - 2015-08-04 17:02 +0100
Re: Source Management Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-03 21:06 +0000
Re: Source Management Arne Vajhøj <arne@vajhoej.dk> - 2015-08-03 21:10 -0400
csiph-web