Reviewed-by: Ronnie Sahlberg <sahlb...@google.com>
On Sat, Sep 6, 2014 at 12:50 AM, Michael Haggerty <mhag...@alum.mit.edu> wrote:
> This makes it obvious that we have no plans to change the integer
> pointed to, which is actually the fd field from a struct lock_file.
>
> Signed-off-by: Michael Haggerty <mhag...@alum.mit.edu>
> ---
> refs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/refs.c b/refs.c
> index 8a63073..21b0da3 100644
> --- a/refs.c
> +++ b/refs.c
> @@ -2218,7 +2218,7 @@ static void write_packed_entry(int fd, char *refname,
> unsigned char *sha1,
> */
> static int write_packed_entry_fn(struct ref_entry *entry, void *cb_data)
> {
> - int *fd = cb_data;
> + const int *fd = cb_data;
> enum peel_status peel_status = peel_entry(entry, 0);
>
> if (peel_status != PEEL_PEELED && peel_status != PEEL_NON_TAG)
> --
> 2.1.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
