From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2012, #04; Tue, 10)
Date: Wed, 11 Apr 2012 08:54:32 -0700 (PDT) [thread overview]
Message-ID: <m3ty0q9sco.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vty0rnrwy.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Will discard shortly unless nothing happens.
Double negation? "Unless nothing"?
> * mk/gitweb-diff-hl (2012-04-05) 8 commits
> * wk/gitweb-snapshot-use-if-modified-since (2012-03-30) 3 commits
What about "[PATCH (bugfix)] gitweb: Fix unintended "--no-merges" for
regular Atom feed" from Sebastian Pipping?
http://thread.gmane.org/gmane.comp.version-control.git/194535/focus=194695
--
Jakub Narebski
next prev parent reply other threads:[~2012-04-11 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 22:27 What's cooking in git.git (Apr 2012, #04; Tue, 10) Junio C Hamano
2012-04-11 15:54 ` Jakub Narebski [this message]
2012-04-11 16:46 ` Junio C Hamano
2012-04-12 6:35 ` Lucian Poston
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=m3ty0q9sco.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).