Re: Tool renames? was Re: First stab at glossary
Junio C Hamano [EMAIL PROTECTED] wrote: I said: I'll draw up a strawman tonight unless somebody else does it first. [...] 3. Non-binaries are called '*-scripts'. In earlier discussions some people seem to like the distinction between *-script and others; I did not particularly like it, but I am throwing this in for discussion. I for one think this makes the command name dependent on a non-essential implementation detail, so -script should go. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Sanity check of git-commit patch, was Re: [PATCH] Making CFLAGS compilant with GNU Coding Standards
Junio C Hamano [EMAIL PROTECTED] wrote: Johannes Schindelin [EMAIL PROTECTED] writes: True. My bad old habit. An elegant method to do that: case --some-long-option in $1*) ..; esac You are almost correct, but you need to realize that I generate that long case -s|--s|--so|--som|... chain using a script that takes all potential option names as its arguments, and makes case arms that contain only unambiguous ones, so that I can handle --some-long-option and --some-other-long-option sensibly. My head spins Isn't it easier to just use getopt(1)? Also you forgot to grok --some-option-with-args=* in your version ;-). Please stop! I'm dizzy already! -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: GIT 0.99.4 (preview)
My proposed patch, the description as is is misleading.
The rest of the .spec file looks sane (yes, I've built my share of RPMs
over the years).
diff --git a/git-core.spec.in b/git-core.spec.in
--- a/git-core.spec.in
+++ b/git-core.spec.in
@@ -2,7 +2,7 @@
Name: git-core
Version: @@VERSION@@
Release: 1
-Vendor:Linus Torvalds [EMAIL PROTECTED]
+Vendor:Junio C Hamano [EMAIL PROTECTED]
Summary: Git core and tools
License: GPL
Group: Development/Tools
@@ -13,22 +13,23 @@ BuildRoot: %{_tmppath}/%{name}-%{version
Prereq:sh-utils, diffutils, rsync, rcs, mktemp = 1.5
%description
-GIT comes in two layers. The bottom layer is merely an extremely fast
-and flexible filesystem-based database designed to store directory trees
-with regard to their history. The top layer is a SCM-like tool which
-enables human beings to work with the database in a manner to a degree
-similar to other SCM tools (like CVS, BitKeeper or Monotone).
+This is a stupid (but extremely fast) directory content manager. It
+doesn't do a whole lot, but what it _does_ do is track directory
+contents efficiently. It is intended to be the base of an efficient,
+distributed source code management system. This package includes
+rudimentary tools that can be used as a SCM, but you should look
+elsewhere for tools for ordinary humans layered on top of this.
%prep
%setup -q
%build
-
make prefix=%{_prefix} all %{!?_without_docs: doc}
%install
rm -rf $RPM_BUILD_ROOT
-make dest=$RPM_BUILD_ROOT prefix=%{_prefix} mandir=%{_mandir} install
install-tools %{!?_without_docs: install-doc}
+make dest=$RPM_BUILD_ROOT prefix=%{_prefix} mandir=%{_mandir} \
+ install install-tools %{!?_without_docs: install-doc}
%clean
rm -rf $RPM_BUILD_ROOT
@@ -43,7 +44,13 @@ rm -rf $RPM_BUILD_ROOT
%{!?_without_docs: %{_mandir}/man7/*.7.gz}
%changelog
+* Sun Aug 07 2005 Horst H. von Brand [EMAIL PROTECTED]
+- Redid the description
+- Cut overlong make line, loosened changelog a bit
+- I think Junio (or perhaps OSDL?) should be vendor...
+
* Thu Jul 14 2005 Eric Biederman [EMAIL PROTECTED]
- Add the man pages, and the --without docs build option
+
* Wed Jul 7 2005 Chris Wright [EMAIL PROTECTED]
- initial git spec file
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, ChileFax: +56 32 797513
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Git 1.0 Synopis (Draft v3
Ryan Anderson [EMAIL PROTECTED] wrote: Source Code Management with Git More bugging... - Either stay with your idea of Git is the idea, git the implementation (iff blessed by the Git Powers That Be) and be consistent about it, or just use git throughout. - Attribute the meaning appropiately, say by: In Linus' own words as the inventor of git: git can mean anything, depending on your mood. - random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of get may or may not be relevant. - stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang. - global information tracker: you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room. - goddamn idiotic truckload of sh*t: when it breaks [...] To get a copy of Git: Daily snapshots are available at: http://www.codemonkey.org.uk/projects/git-snapshots/git/ (Thanks to Dave Jones) Source tarballs and RPMs at: http://www.kernel.org/pub/software/scm/git/ Deb packages at: insert url here Or via Git itself: git clone http://www.kernel.org/pub/scm/git/git.git/ local directory git clone rsync://rsync.kernel.org/pub/scm/git/git.git/ local directory (rsync is generally faster for an initial clone, you can switch later by editing .git/branches/origin and changing the url) To get the 'Porcelain' tools mentioned above: SCM Interface layers: cogito - http://www.kernel.org/pub/software/scm/cogito/ StGIT - http://www.procode.org/stgit/ At least cogito includes a (slightly old) version of git. Dunno about StGIT. And git and cogito have a gitk inside too. This should be mentioned, i.e., look at the package(s) you are interested and see what else they carry or require and keep in mind that (for now?) getting git as part of one package is /not/ guaranteed to be compatible with another or standard git. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Git 1.0 Synopis (Draft v3
Sam Ravnborg [EMAIL PROTECTED] wrote: On Fri, Jul 29, 2005 at 04:29:41AM -0400, Ryan Anderson wrote: Source Code Management with Git The article should include a HOWTO part alos. I'd vote for a separate file. So people can see how to edit a file, pull from a remote repository etc. Exactly. Since you have introduced core and porcelains it would be most logical to use one of the porcelains in these examples, maybe accompanied by the raw git commands being executed. Better leave the Porcelain-HOWTO to individual Porcelain. Perhaps the Plumbing-HOWTO should include a section on interfacing to Porcelain (or it should be yet another file). -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Git 1.0 Synopis (Draft v3
[Yes, I know it is considered odd when you speak to yourself in public...] Horst von Brand [EMAIL PROTECTED] wrote: Ryan Anderson [EMAIL PROTECTED] wrote: Source Code Management with Git More bugging... And then some. To get the 'Porcelain' tools mentioned above: SCM Interface layers: cogito - http://www.kernel.org/pub/software/scm/cogito/ StGIT - http://www.procode.org/stgit/ At least cogito includes a (slightly old) version of git. Dunno about StGIT. And git and cogito have a gitk inside too. This should be mentioned, i.e., look at the package(s) you are interested and see what else they carry or require and keep in mind that (for now?) getting git as part of one package is /not/ guaranteed to be compatible with another or standard git. Also note that StGIT is /not/ a SCM (as cogito is), it is a tool to shuffle patches that uses git as a backend/target. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trial git RPM's..
Linus Torvalds [EMAIL PROTECTED] wrote: On Mon, 11 Jul 2005, Eric W. Biederman wrote: A couple of pieces. The dist target has assumes git-tar-tree is in the path. Making it so you have to have git installed to build the rpm. Yes. Maybe we could relax that requirement by using ./git-tar-tree or something? That still requires that you have _built_ git to do the rpm, but at least you won't have had to install it. I don't see a problem here. Sure, you need git to build git, so place it in Build-requires: Need to install the binary to build the next from source, that's all. Just like gcc ;-) [...] The man pages are not built. The build dependencies do not call out the tools necessary to build the man pages. Most people don't have asciidoc, and I'm not sure we want to require it. Maybe we could have a separate make man-rpm target for that? Would have to be a requirement for building anyway. There is a (not really nice) SRPM at http://www.pvv.ntnu.no/~terjeros/rpms/asciidoc/. Will see to clean it up. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: BUG: cg-clone accepts '_' in git_ssh: URI's, but cg-push does not.
John Ellson [EMAIL PROTECTED] wrote: BUG: cg-clone accepts '_' in git+ssh: URI's, but cg-push does not. Right. '_' is illegal in domain names... -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
