From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] update grub web page with reference to GIT instead of bzr.
Date: Sun, 27 Oct 2013 20:11:13 +0400 [thread overview]
Message-ID: <20131027201113.2d33a4ff@opensuse.site> (raw)
In-Reply-To: <526D3901.10005@gmail.com>
В Sun, 27 Oct 2013 11:02:09 -0500
Bruce Dubbs <bruce.dubbs@gmail.com> пишет:
> Andrey Borzenkov wrote:
> > В Sun, 27 Oct 2013 19:24:28 +0400
> > Andrey Borzenkov <arvidjaar@gmail.com> пишет:
> >
> >>
> >> That's where website lags behind. GRUB switched to GIT a while ago. See
> >>
> >> https://savannah.gnu.org/git/?group=grub
> >>
> >> As for web site - I do not know; Vladimir, who can edit this?
> >>
> >
> > Not sure if I can commit, but - does below look sane?
>
> The files are actually maintained via templates and a Makefile to attach
> headers and footers that can be updated easily. The file that you want
> to change is templates/grub-download.body.
>
Usually generated files are not placed under SCM control ... thank you
for the hint.
> If you do have commit privs, please do not update the html directly.
>
I do not know until I try :) Feel free to commit.
Index: templates/grub-download.body
===================================================================
RCS file: /web/grub/grub/templates/grub-download.body,v
retrieving revision 1.1
diff -u -p -r1.1 grub-download.body
--- templates/grub-download.body 5 Jan 2012 23:35:45 -0000 1.1
+++ templates/grub-download.body 27 Oct 2013 16:09:34 -0000
@@ -8,29 +8,18 @@ site <a href="ftp://ftp.gnu.org/gnu/grub
</p>
<p> All the development is done through a <a
-href="http://bazaar.canonical.com/" >Bazaar</a> repository. If you are
+href="http://git-scm.com/" >GIT</a> repository. If you are
interested in the cutting-edge version of GNU GRUB, for example, to test a
newer version or to add new features, we strongly recommend giving the latest
repository version a try. You can obtain the latest GRUB source from the
-Bazaar:</p>
+GIT:</p>
-<pre><code>bzr branch http://bzr.savannah.gnu.org/r/grub/trunk/grub</code></pre>
+<pre><code>git clone git://git.savannah.gnu.org/grub.git</code></pre>
<p>For developers with write access via ssh, use:</p>
-<pre><code>bzr branch bzr+ssh://<membername>@bzr.savannah.gnu.org/grub/trunk/grub</code></pre>
+<pre><code>git clone <membername>@git.sv.gnu.org:/srv/git/grub.git</code></pre>
-<p>You can also use scp and rsync if needed.</p>
-
-<p>In the Bazaar repository, a number of other development trees may be found.
-Notably the experimental branch of GRUB is a staging area where less tested (or
-more intrusive) changes are put before they are merged into trunk.
-</p>
-
-<p>Other branches are listed at the GRUB <a
-href="http://bzr.savannah.gnu.org/r/grub/branches/">branch index</a> and <a
-href="http://bzr.savannah.gnu.org/r/grub/people/">individual developer
-repositories</a>. These branches are not browsable, but can be checked
-out with Bazaar.</p>
+<p>You can also use HTTP if needed.</p>
[% INCLUDE footer %]
next prev parent reply other threads:[~2013-10-27 16:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 15:36 BUGS: btrfs multi-device support fixes Gene Czarcinski
2013-10-26 16:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-26 20:16 ` Gene Czarcinski
2013-10-27 6:54 ` Andrey Borzenkov
2013-10-27 14:47 ` Gene Czarcinski
2013-10-27 15:24 ` Andrey Borzenkov
2013-10-27 15:46 ` [PATCH] update grub web page with reference to GIT instead of bzr Andrey Borzenkov
2013-10-27 16:02 ` Bruce Dubbs
2013-10-27 16:11 ` Andrey Borzenkov [this message]
2013-10-27 16:23 ` Bruce Dubbs
2013-10-27 16:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-27 17:17 ` Bruce Dubbs
2013-10-27 16:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-27 15:51 ` BUGS: btrfs multi-device support fixes Bruce Dubbs
2013-10-27 16:00 ` Andrey Borzenkov
2013-10-27 17:51 ` Gene Czarcinski
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=20131027201113.2d33a4ff@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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).