GitHub/gf-core
1
0
Fork 1
mirror of https://github.com/GrammaticalFramework/gf-core.git synced 2026-04-11 22:09:32 -06:00
Code Issues Packages Projects Releases Wiki Activity

Added darcs add to darcs instructions.

Browse Source
This commit is contained in:
bringert
2006-09-03 20:14:10 +00:00
parent fda42f61c4
commit 952c612703
2 changed files with 49 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
doc/darcs.html
View File

@@ -8,7 +8,7 @@
<P ALIGN="center"><CENTER><H1>GF Darcs repository</H1>
<FONT SIZE="4">
<I>Author: Björn Bringert &lt;bringert@cs.chalmers.se&gt;</I><BR>
Last update: Mon Aug 28 14:11:23 2006
Last update: Sun Sep 3 22:14:06 2006
</FONT></CENTER>
<P></P>
@@ -122,7 +122,18 @@ Without <CODE>-a</CODE>, you can choose which patches you want to get.
<H2>Recording local changes</H2>
<P>
Since every copy is a repository, you can have local version control
of your changes. To record some changes, use:
of your changes.
</P>
<P>
If you have added files, you first need to tell your local repository to
keep them under revision control:
</P>
<PRE>
$ darcs add file1 file2 ...
</PRE>
<P></P>
<P>
To record changes, use:
</P>
<PRE>
$ darcs record
@@ -130,7 +141,15 @@ of your changes. To record some changes, use:
<P></P>
<P>
This creates a patch against the previous version and stores it in your
local repository.
local repository. You can record any number of changesets before
pushing them to the main repo. In fact, you don't have to push them at
all if you want to keep the changes only in your local repo.
</P>
<P>
If you think there are too many questions about what to record, you
can use the <CODE>-a</CODE> flag to <CODE>record</CODE>. Or answer <CODE>a</CODE> to the first
question. Both of these record all the changes you have in your local
repository.
</P>
<A NAME="toc7"></A>
<H2>Submitting patches</H2>
@@ -232,23 +251,12 @@ Without <CODE>-a</CODE>, you can choose which patches you want to get.
<H2>Commit your changes</H2>
<P>
There are two steps to commiting a change to the main repo. First you
have to record the changes that you want to commit:
</P>
<PRE>
$ darcs record
</PRE>
<P></P>
<P>
This creates a patch against the previous version and stores it in your
local repository. You can record any number of changesets before
pushing them to the main repo. In fact, you don't have to push them at
all if you want to keep the changes only in your local repo.
have to record the changes that you want to commit, then you push them
to the main repo.
</P>
<P>
If you think there are too many questions about what to record, you
can use the <CODE>-a</CODE> flag to <CODE>record</CODE>. Or answer <CODE>a</CODE> to the first
question. Both of these record all the changes you have in your local
repository.
For instructions on recording your changes locally,
see "Recording local changes" above.
</P>
<P>
Then you can push the patch(es) to the main repo. If you are using

39
doc/darcs.txt
View File

@@ -77,14 +77,31 @@ Without ``-a``, you can choose which patches you want to get.
== Recording local changes ==
Since every copy is a repository, you can have local version control
of your changes. To record some changes, use:
of your changes.
If you have added files, you first need to tell your local repository to
keep them under revision control:
```
$ darcs add file1 file2 ...
```
To record changes, use:
```
$ darcs record
```
This creates a patch against the previous version and stores it in your
local repository.
local repository. You can record any number of changesets before
pushing them to the main repo. In fact, you don't have to push them at
all if you want to keep the changes only in your local repo.
If you think there are too many questions about what to record, you
can use the ``-a`` flag to ``record``. Or answer ``a`` to the first
question. Both of these record all the changes you have in your local
repository.
== Submitting patches ==
@@ -180,21 +197,11 @@ Without ``-a``, you can choose which patches you want to get.
== Commit your changes ==
There are two steps to commiting a change to the main repo. First you
have to record the changes that you want to commit:
have to record the changes that you want to commit, then you push them
to the main repo.
```
$ darcs record
```
This creates a patch against the previous version and stores it in your
local repository. You can record any number of changesets before
pushing them to the main repo. In fact, you don't have to push them at
all if you want to keep the changes only in your local repo.
If you think there are too many questions about what to record, you
can use the ``-a`` flag to ``record``. Or answer ``a`` to the first
question. Both of these record all the changes you have in your local
repository.
For instructions on recording your changes locally,
see "Recording local changes" above.
Then you can push the patch(es) to the main repo. If you are using
ssh-access, all you need to do is: