<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tools/git-repo.git, branch v1.6.8</title>
<subtitle>Mirror of gerrit.googlesource.com/git-repo</subtitle>
<id>https://git.enea.com/cgit/tools/git-repo.git/atom?h=v1.6.8</id>
<link rel='self' href='https://git.enea.com/cgit/tools/git-repo.git/atom?h=v1.6.8'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/'/>
<updated>2009-06-02T22:08:45+00:00</updated>
<entry>
<title>Delete empty parent subdirs after deleting obsolete paths.</title>
<updated>2009-06-02T22:08:45+00:00</updated>
<author>
<name>Jaikumar Ganesh</name>
<email>jaikumar@google.com</email>
</author>
<published>2009-06-02T22:07:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=8135cdc53c8737c242a5ba122491c9308a3407d8'/>
<id>urn:sha1:8135cdc53c8737c242a5ba122491c9308a3407d8</id>
<content type='text'>
After sync, we delete obsolete project paths.
Iterate and delete parent subdirs which are empty.
Tested on projects within subdirectories.
</content>
</entry>
<entry>
<title>Update project paths after sync.</title>
<updated>2009-06-02T18:00:53+00:00</updated>
<author>
<name>Jaikumar Ganesh</name>
<email>jaikumar@google.com</email>
</author>
<published>2009-06-02T04:10:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=4f2517ff1174cd485f0ac93705b0fa9348595f6f'/>
<id>urn:sha1:4f2517ff1174cd485f0ac93705b0fa9348595f6f</id>
<content type='text'>
After a repo sync, some of the project paths might need
to be removed. This changes maintains a list of project
paths from the previous sync operation and compares.
</content>
</entry>
<entry>
<title>Fix unnecessary self in project.py</title>
<updated>2009-06-01T22:28:21+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-06-01T22:28:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=fe200eeb520e1b50c00d359ca9e138f6149ce0f2'/>
<id>urn:sha1:fe200eeb520e1b50c00d359ca9e138f6149ce0f2</id>
<content type='text'>
Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
<entry>
<title>Add PyDev project files to repo</title>
<updated>2009-06-01T22:09:07+00:00</updated>
<author>
<name>Kis Gergely</name>
<email>gergely.kis@mattakis.com</email>
</author>
<published>2009-06-01T21:35:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=078a8b270ff7b8b8c3da5029b1d3ff690fb94cc1'/>
<id>urn:sha1:078a8b270ff7b8b8c3da5029b1d3ff690fb94cc1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Change project.revision to revisionExpr and revisionId</title>
<updated>2009-05-30T01:45:20+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-05-30T01:38:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=3c8dea1f8d7c4257d080f9f34159cdb2fffb81e6'/>
<id>urn:sha1:3c8dea1f8d7c4257d080f9f34159cdb2fffb81e6</id>
<content type='text'>
The revisionExpr field now holds an expression from the manifest,
such as "refs/heads/master", while revisionId holds the current
commit-ish SHA-1 of the revisionExpr.  Currently that is only
filled in if the manifest points directly to a SHA-1.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
<entry>
<title>Change DWIMery hack for dealing with rewound remote branch</title>
<updated>2009-05-30T01:45:17+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-05-30T01:28:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=8ad8a0e61d919e76f521f3124c91bd46fbaa84e2'/>
<id>urn:sha1:8ad8a0e61d919e76f521f3124c91bd46fbaa84e2</id>
<content type='text'>
The trick of looking at the reflog for the remote tracking branch
and only going back one commit works some of the time, but not all of
the time.  Its sort of relying on the fact that the user didn't use
`repo sync -n` or `git fetch` to only update the tracking branches
and skip the working directory update.

Doing this right requires looking through the history of the SHA-1
source (what the upstream used to be) and finding a spot where the
DAG diveraged away suddenly, and consider that to be the rewind
point.  That's really difficult to do, as we don't have a clear
picture of what that old point was.

A close approximation is to list all of the commits that are in
HEAD, but not the new upstream, and rebase all of those where the
committer email address is this user's email address.  In most cases,
this will effectively rebase only the user's new original work.

If the user is the project maintainer and rewound the branch
themselves, and they don't want all of the commits they have created
to be rebased onto the new upstream, they should handle the rebase
on their own, after the sync is complete.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
<entry>
<title>Refactor how projects parse remotes so it can be replaced</title>
<updated>2009-05-29T16:31:28+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-05-19T21:58:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=d1f70d9929ddd2748ccc9c1dd2f9603068e1f3e6'/>
<id>urn:sha1:d1f70d9929ddd2748ccc9c1dd2f9603068e1f3e6</id>
<content type='text'>
We now feed Project a RemoteSpec, instead of the Remote directly
from the XmlManifest.  This way the RemoteSpec already has the
full project URL, rather than just the base, permitting other
types of manifests to produce the URL in their own style.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
<entry>
<title>Refactor Manifest to be XmlManifest</title>
<updated>2009-05-29T16:31:28+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-05-18T20:19:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=c8a300f6397dad7db00c3654ff6e50e9519ed7c9'/>
<id>urn:sha1:c8a300f6397dad7db00c3654ff6e50e9519ed7c9</id>
<content type='text'>
We'll soon be supporting two different manifest formats, but we
can't immediately remove support for the current XML one that is
in wide spread use within Android.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
<entry>
<title>Allow callers of GitConfig to specify the pickle file path</title>
<updated>2009-05-29T16:31:00+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-05-22T01:52:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=1b34c9118ed86a15b0bc1094804c095dd7be33cb'/>
<id>urn:sha1:1b34c9118ed86a15b0bc1094804c095dd7be33cb</id>
<content type='text'>
This way we can put it in another directory than the config file
itself, e.g. hide it inside ".git" when parsing a ".gitmodules"
file from the working tree.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
<entry>
<title>Teach GitConfig how to yield subsection names</title>
<updated>2009-05-19T20:02:00+00:00</updated>
<author>
<name>Shawn O. Pearce</name>
<email>sop@google.com</email>
</author>
<published>2009-05-19T19:47:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/tools/git-repo.git/commit/?id=366ad214b82cadc32920b371f7f99f3f6894ec6f'/>
<id>urn:sha1:366ad214b82cadc32920b371f7f99f3f6894ec6f</id>
<content type='text'>
This can be useful when pulling apart a configuration file, like
finding all entries which match submodule.*.*.

Signed-off-by: Shawn O. Pearce &lt;sop@google.com&gt;
</content>
</entry>
</feed>
