Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6068859
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T09:45:36+00:00 2026-05-23T09:45:36+00:00

In gitdiffcore(7) it simply states: The pathspecs are used to limit the world diff

  • 0

In gitdiffcore(7) it simply states:

The pathspecs are used to limit the world diff operates in. 
They remove the filepairs outside the specified sets of pathnames. 
E.g. If the input set of filepairs included:

    :100644 100644 bcd1234... 0123456... M junkfile

My question is how to read this, i.e. which fields are which, and what should they represent?

I’m looking so that I can understand if there is any mileage in detecting pathname changes (as an option) separately from the file rename detection which is both expensive and tends to suggest to users that many files have been renamed (rather than a single path change)

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T09:45:37+00:00Added an answer on May 23, 2026 at 9:45 am

    let’s break this down:

    :100644        100644         bcd1234...     0123456...     M         junkfile
    old file mode  new file mode  old file hash  new file hash  modified  file name
    

    to create archives with a given name from a directory at a specified commit, use the git archive command:

    git archive --prefix='your_product_v1.2/' -o 'your_product.zip' v1.2:path/to/directory/
    

    assuming, you want to create an archive from path/to/directory/ as it was in version v.1 (tag, branch, you can even use a commit id here). the archive will be named your_product.zip (format inferred from file name, .tar is also possible), and all files will be placed in the subfolder your_product_v1.2 inside the zip file.

    this way you don’t have to rename the directory inside your VCS (why would you do that anyways?). hope that helps! leave a comment if things are still unclear.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.