 d7c411b71d
			
		
	
	d7c411b71d
	
	
	
		
			
			When pushing via builtin transports (like file://, git://), the underlying transport helper (in this case, git-pack-objects) did not get the --progress option, even if it was passed to git push. Fix this, and update the tests to reflect this. Note that according to the git-pack-objects documentation, we can safely apply the usual --progress semantics for the transport commands like clone and fetch (and for pushing over other smart transports). Reported-by: Chase Brammer <cbrammer@gmail.com> Helped-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Tay Ray Chuan <rctay89@gmail.com> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
		
			
				
	
	
		
			22 lines
		
	
	
		
			403 B
		
	
	
	
		
			C
		
	
	
	
	
	
			
		
		
	
	
			22 lines
		
	
	
		
			403 B
		
	
	
	
		
			C
		
	
	
	
	
	
| #ifndef SEND_PACK_H
 | |
| #define SEND_PACK_H
 | |
| 
 | |
| struct send_pack_args {
 | |
| 	unsigned verbose:1,
 | |
| 		quiet:1,
 | |
| 		porcelain:1,
 | |
| 		progress:1,
 | |
| 		send_mirror:1,
 | |
| 		force_update:1,
 | |
| 		use_thin_pack:1,
 | |
| 		use_ofs_delta:1,
 | |
| 		dry_run:1,
 | |
| 		stateless_rpc:1;
 | |
| };
 | |
| 
 | |
| int send_pack(struct send_pack_args *args,
 | |
| 	      int fd[], struct child_process *conn,
 | |
| 	      struct ref *remote_refs, struct extra_have_objects *extra_have);
 | |
| 
 | |
| #endif
 |