From: Jason Riedy <ejr@EECS.Berkeley.EDU>
To: git@vger.kernel.org
Subject: Re: [PATCH] Add ALL_LDFLAGS to the git target.
Date: Tue, 28 Mar 2006 15:59:37 -0800 [thread overview]
Message-ID: <16397.1143590377@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <7vbqvqjgvi.fsf@assigned-by-dhcp.cox.net>
And Junio C Hamano writes:
- My preference is to ignore FORTRAN, keep Mark's current rules,
- perhaps with a way to turn it off if people really find it
- annoying (I do not mind having it always on).
Sorry; I had meant my comment as an aside and not a
request. I had never noticed the function definition
in patches, and now I typically use Emacs's tools.
And as of Fortran 90, it's now officially Fortran and
not FORTRAN.
Jason
next prev parent reply other threads:[~2006-03-28 23:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:28 What's in git.git Junio C Hamano
2006-03-28 1:15 ` [PATCH] Add ALL_LDFLAGS to the git target Jason Riedy
2006-03-28 1:25 ` Junio C Hamano
2006-03-28 3:11 ` Jason Riedy
2006-03-28 6:21 ` Junio C Hamano
2006-03-28 19:46 ` Jason Riedy
2006-03-28 22:48 ` Mark Wooding
2006-03-28 23:03 ` Linus Torvalds
2006-03-28 23:20 ` Junio C Hamano
2006-03-28 23:59 ` Jason Riedy [this message]
2006-03-29 0:01 ` Junio C Hamano
2006-03-28 23:21 ` Mark Wooding
2006-03-29 0:16 ` [PATCH] Support for pickaxe matching regular expressions Petr Baudis
2006-03-29 13:09 ` Petr Baudis
2006-03-29 11:42 ` [PATCH] Add ALL_LDFLAGS to the git target Johannes Schindelin
2006-03-28 2:05 ` Gitk strangeness Linus Torvalds
2006-03-28 2:12 ` Junio C Hamano
2006-03-28 2:31 ` Paul Mackerras
2006-03-28 2:52 ` Linus Torvalds
2006-03-28 2:54 ` Junio C Hamano
2006-03-28 4:31 ` Paul Mackerras
2006-03-28 5:38 ` Junio C Hamano
2006-03-28 6:18 ` Paul Mackerras
2006-03-28 7:52 ` Junio C Hamano
2006-03-28 22:51 ` Paul Mackerras
2006-03-29 0:50 ` Junio C Hamano
2006-03-29 6:41 ` Junio C Hamano
2006-03-30 20:57 ` Alex Riesen
2006-03-30 22:33 ` Paul Mackerras
2006-03-30 23:46 ` Paul Mackerras
2006-03-31 1:50 ` Junio C Hamano
2006-03-31 6:27 ` Alex Riesen
2006-03-28 2:57 ` Linus Torvalds
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=16397.1143590377@lotus.CS.Berkeley.EDU \
--to=ejr@eecs.berkeley.edu \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.