Thread (3 messages) flat view 3 messages, 2 authors, 2016-06-15

Re: [PATCH 4/8] Allow fetch to modify refs

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:47:21

Hi,

On Thu, 3 Sep 2009, Daniel Barkalow wrote:
+	/**
+	 * Fetch the objects for the given refs. Note that this gets
+	 * an array, and should ignore the list structure.
This is not clear at all.  You should rather say "[...] and should not 
look at, or set, the 'next' member of the refs".
+	 *
+	 * If the transport did not get hashes for refs in
+	 * get_refs_list(), it should set the old_sha1 fields in the
+	 * provided refs now.
Not the "new_sha1"?
+	 **/
+	int (*fetch)(struct transport *transport, int refs_nr, struct ref **refs);
+
[...]
+	/** get_refs_list(), fetch(), and push_refs() can keep
The "/**" wants to have a line to itself.
+	 * resources (such as a connection) reserved for futher
+	 * use. disconnect() releases these resources.
+	 **/
 	int (*disconnect)(struct transport *connection);
 	char *pack_lockfile;
 	signed verbose : 2;
Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help