From: "Arend van Spriel" <arend@broadcom.com>
To: sedat.dilek@gmail.com
Cc: webmaster@kernel.org, "Konstantin Ryabitsev" <mricon@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [git.k.o] gitweb->cgit: Re-add Git snapshot tarball feature
Date: Sun, 3 Mar 2013 12:49:41 +0100 [thread overview]
Message-ID: <513338D5.4010302@broadcom.com> (raw)
In-Reply-To: <CA+icZUUWqeHdgjP-Hi630DDwO65evWUUCX2tBYfj=Cn1w3dEAg@mail.gmail.com>
On 03/03/13 12:34, Sedat Dilek wrote:
> Hi,
>
> unfortunately, the Git snapshot tarball feature was dropped when
> switching from gitweb->cgit interface.
Just curious. I am looking at gitweb and cgit for our internal
repositories and still deciding so I would like to know what "your" main
motivation was to move kernel.org over to cgit.
Gr. AvS
next prev parent reply other threads:[~2013-03-03 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 11:34 [git.k.o] gitweb->cgit: Re-add Git snapshot tarball feature Sedat Dilek
2013-03-03 11:49 ` Arend van Spriel [this message]
2013-03-03 13:53 ` Konstantin Ryabitsev
2013-03-03 14:13 ` Sedat Dilek
2013-03-03 14:17 ` Sedat Dilek
2013-03-03 14:22 ` Konstantin Ryabitsev
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=513338D5.4010302@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mricon@kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=webmaster@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox