public inbox for frysk-cvs@sourceware.org help / color / mirror / Atom feed
From: moore@sourceware.org To: frysk-cvs@sourceware.org Subject: [SCM] master: Removed references to CVS and added pointers to Git docs Date: Thu, 10 Jan 2008 16:49:00 -0000 [thread overview] Message-ID: <20080110164917.12335.qmail@sourceware.org> (raw) The branch, master has been updated via 87bc11379df13e358e67a9c37206c3d52f13a5eb (commit) from 1456b388ea0d5e4a96e53de9150bf857c7c2b899 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 87bc11379df13e358e67a9c37206c3d52f13a5eb Author: Tim Moore <moore@blackbox.bricoworks.com> Date: Thu Jan 10 17:46:21 2008 +0100 Removed references to CVS and added pointers to Git docs ----------------------------------------------------------------------- Summary of changes: htdocs/build/git-fu.html | 2 +- htdocs/build/index.html | 29 ++++++++++++++++------------- htdocs/build/rhel/index.html | 2 +- htdocs/getinvolved/index.html | 21 +++++++-------------- 4 files changed, 25 insertions(+), 29 deletions(-) First 500 lines of diff: diff --git a/htdocs/build/git-fu.html b/htdocs/build/git-fu.html index 6dbbaa8..67adc9e 100644 --- a/htdocs/build/git-fu.html +++ b/htdocs/build/git-fu.html @@ -69,7 +69,7 @@ <td valign="top"> <!-- start text --> <p> -<em>frysk</em> is changing from CVS +<em>frysk</em> has changed from CVS to <a href="http://www.kernel.org/pub/software/scm/git/docs/">Git</a> for its source control system. This page is meant to ease the transition for new Git users and point the way towards the more diff --git a/htdocs/build/index.html b/htdocs/build/index.html index 15df093..6da2c14 100644 --- a/htdocs/build/index.html +++ b/htdocs/build/index.html @@ -430,22 +430,17 @@ Use <tt>CNTRL-B</tt>. </dl> <h3><a name="faq-git">GIT Questions, with Answers</h3></a> +<p>See our <a href="git-fu.html">Git page</a> for examples of working + with Git. +</p> <dl> -<dt> -<a name="How do I cut a branch?"> -How do I cut a branch?</dt></a> <dd><br>This needs to be rewritten for -Git.<br>First choose a name for your branch, it should include both -your user name, a terse hint as to the branches purpose, and todays -date. For instance <tt>pmuldoon-fcore-20061101</tt>, or -<tt>cagney-triage12345-20061122</tt>. Two tags will be created, first -one for the branch point, and second one for the branch: - -<pre> -$ cvs -d:.. rtag BRANCH-branchpoint frysk -$ cvs -d... rtag -r BRANCH-branchpoint -b BRANCH-branch frysk -</pre> +<dt>How do I cut a branch?</dt> +<dd> See our Git page's <a href="git-fu.html#branches">section on + branches</a>. A good Git practice is to take advantage of the + hierarchical nature of branch names and give short-lived "topic" + branches names like <tt>topic/regsbugfix</tt>. </dd> <dt>How do I import a third party package into frysk-imports?</dt> @@ -533,6 +528,14 @@ Comments on how to improve this process appreciated. </dd> +<dt>How do I create a tag or a branch at a certain date?</dt> +<dd>There isn't a direct command for doing this in Git. Instead, you + can find the SHA1 hash of the last commit before a date with: +<p><pre> +git-rev-list --before=2007-12-14 --pretty=oneline -n1 HEAD +</pre> +and make the branch or tag using the hash. +</dd> </dl> <!-- end text --> diff --git a/htdocs/build/rhel/index.html b/htdocs/build/rhel/index.html index 34009c1..701c44d 100644 --- a/htdocs/build/rhel/index.html +++ b/htdocs/build/rhel/index.html @@ -87,7 +87,7 @@ bug. Red Hat Enterprise Linux 4 Update 3 and later include <tt>gcc4</tt> and <tt><em>frysk</em></tt> RPMs that contain everything needed to -build <em>frysk</em> from <tt>CVS</tt>; just install RPMs for the following: +build <em>frysk</em> from Git; just install RPMs for the following: <pre> up2date make transfig \ diff --git a/htdocs/getinvolved/index.html b/htdocs/getinvolved/index.html index aaef2b5..7665a7a 100755 --- a/htdocs/getinvolved/index.html +++ b/htdocs/getinvolved/index.html @@ -133,18 +133,11 @@ standard sourceware-style services.</p> <ul> -<li><b>Anonymous CVS</b> <br>First login to the CVS server as -anonymous: +<li><b>Git</b> <br>Use Git to clone the <em>frysk</em> repository and check +out the sources: <pre> -cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/frysk login -</pre> - -{enter "anoncvs" as the password}<br> -The list of modules can then be listed with: - -<pre> -cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/frysk co -c +git-clone git://sourceware.org/git/frysk.git </pre> Details on how to build and run <em>frysk</em> can be found on the <a @@ -152,13 +145,13 @@ href="../build/">build</a> page. </li> -<li><b>Web CVS</b> <br> The <em>frysk</em> sources can be browsed <a -href="http://sources.redhat.com/cgi-bin/cvsweb.cgi/?cvsroot=frysk">using -cvsweb</a>. </li> +<li><b>Web Git</b> <br> The <em>frysk</em> sources can be browsed <a +href="http://sourceware.org/git/?p=frysk.git;a=summary">using +gitweb</a>. </li> </ul> -<p>People needing CVS write access can request it using <a +<p>People needing write access to the Git repository can request it using <a href="http://sources.redhat.com/cgi-bin/pdw/ps_form.cgi">this handy form</a></p> hooks/post-receive -- frysk system monitor/debugger
reply other threads:[~2008-01-10 16:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080110164917.12335.qmail@sourceware.org \ --to=moore@sourceware.org \ --cc=frysk-cvs@sourceware.org \ --cc=frysk@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).