From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: Weird shallow-tree conversion state, and branches of shallow trees
Date: Tue, 17 Apr 2007 22:51:18 +0100 [thread overview]
Message-ID: <200704172251.20831.andyparkins@gmail.com> (raw)
In-Reply-To: <7v8xcqofru.fsf@assigned-by-dhcp.cox.net>
On Tuesday 2007, April 17, Junio C Hamano wrote:
> Andy Parkins <andyparkins@gmail.com> writes:
> > However, it's missing the point to take my example as an unsolved
> > problem - there are plenty of ways I can get what I want; I brought
> > it up merely as a counter to the statement that there were no valid
> > situations for wanting keyword expansion.
>
> That's actually quite different from what you said.
Sorry; I didn't express it very well - the thing that started all this
was the statement that there was no valid use case for keywords. I
just gave an example. I felt that the thread was moving away from
keywords and towards solving my particular problem - which is all
appreciated, but wasn't the point. Running makefile recipes or extra
scripts are all valid methods and pragmatic
working-with-what-git-does-now solutions. I wanted to distinguish
between what I could do now and what I could do with keyword support.
> You were claiming that with built-in keyword expansion what you
> want becomes /simpler/. I questioned that.
Well it does from the point of view of pressing "print".
> Maybe it's just me, who is not a GUI person [*1*], but to me,
> having to start inkscape, mouse around to find the "Print"
> button and print feels much more cumbersome than simply typing
> "make print".
Again, that was addressing my particular problem - good stuff. However,
it's just luck that inkscape has a batch mode - there's no guarantee
for that.
I could just swap the example around a bit, what about if it was an
OpenOffice document that I want to have transparent
compression/decompression and I've set the properties tag to
contain "$Id$". There is no amount of scripting that will enable batch
printing of that.
Anyway - I've wasted enough of your time with this foolishness now.
It's dropped, consider me silenced on this subject ;-)
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-04-17 21:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 0:53 Weird shallow-tree conversion state, and branches of shallow trees Robin H. Johnson
2007-04-14 8:56 ` Johannes Schindelin
2007-04-15 0:03 ` Robin H. Johnson
2007-04-15 0:02 ` David Lang
2007-04-15 2:01 ` Robin H. Johnson
2007-04-15 4:31 ` Shawn O. Pearce
2007-04-15 5:57 ` Nguyen Thai Ngoc Duy
2007-04-15 8:54 ` Jakub Narebski
2007-04-15 18:18 ` Linus Torvalds
2007-04-15 19:51 ` Andy Parkins
2007-04-15 20:51 ` Linus Torvalds
2007-04-16 0:11 ` Bill Lear
2007-04-16 9:10 ` Andy Parkins
2007-04-16 15:17 ` Julian Phillips
2007-04-16 2:17 ` Robin H. Johnson
2007-04-16 3:01 ` Theodore Tso
2007-04-16 3:23 ` Nguyen Thai Ngoc Duy
2007-04-16 15:08 ` Linus Torvalds
2007-04-16 16:06 ` Nguyen Thai Ngoc Duy
2007-04-16 3:32 ` Robin H. Johnson
2007-04-16 17:00 ` Linus Torvalds
2007-04-17 4:16 ` Daniel Barkalow
2007-04-16 14:59 ` Linus Torvalds
2007-04-16 9:03 ` Andy Parkins
2007-04-16 15:54 ` Sven Verdoolaege
2007-04-16 15:58 ` Linus Torvalds
2007-04-16 23:25 ` Weird shallow-tree conversion state, and branches of shallowtrees David Lang
2007-04-17 19:50 ` David Lang
2007-04-17 9:45 ` Weird shallow-tree conversion state, and branches of shallow trees Andy Parkins
2007-04-16 19:41 ` Junio C Hamano
2007-04-16 20:55 ` Andy Parkins
2007-04-17 21:24 ` Junio C Hamano
2007-04-17 21:51 ` Andy Parkins [this message]
2007-04-15 9:44 ` Robin H. Johnson
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=200704172251.20831.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pclouds@gmail.com \
--cc=robbat2@gentoo.org \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.org \
/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).